chore(deps-dev): bump cpp-linter from 1.14.1 to 1.15.1 in the org group across 1 directory by dependabot[bot] · Pull Request #501 · cpp-linter/cpp-linter-action

dependabot · 2026-10-15T18:53:17Z

Bumps the org group with 1 update in the / directory: cpp-linter.

Updates cpp-linter from 1.14.1 to 1.15.1

Release notes

v1.15.1

🐛 Bug fixes

fix: support a --repo-root in a sub-folder of the git repo by @shenxianpeng in #247

fix: stop changing into --repo-root and only accept one inside the working directory by @shenxianpeng in #246

fix: raise when git cannot read the original file by @shenxianpeng in #242

fix: replace pygit2 with a git diff subprocess by @shenxianpeng in #240

📝 Documentation updates

docs: fix outdated CI note, docs build steps and CLI doc generation by @shenxianpeng in #238

docs: add Google Analytics and a sitemap by @shenxianpeng in #237

✍ Other changes

test: cover missing-token exits and 404 responses by @shenxianpeng in #249

chore(dev): test against Python 3.15 and the 3.16 pre-release by @shenxianpeng in #241

chore: count only binary downloads in funding.json by @shenxianpeng in #243

📦 Dependency updates

build(deps): bump certifi from 2025.10.5 to 2026.10.19 by @dependabot[bot] in #244

build: bump git-bot-feedback from 0.2.6 to 0.2.9 by @2bndy5 in #239

chore: update pre-commit hooks by @shenxianpeng in #235

Full Changelog: cpp-linter/cpp-linter@v1.15.0...v1.15.1

v1.15.0

🚀 New features and improvements

feat: migrate to git-bot-feedback by @2bndy5 in #226

feat: redesign the comment footer with website, star and sponsor links by @shenxianpeng in #228

🐛 Bug fixes

fix: use git, not the GitHub API, outside GitHub Actions by @shenxianpeng in #221

docs: link the logging levels to the Python docs by @shenxianpeng in #218

👷 Changes for developers

chore(dev): limit concurrent workflow runs by @2bndy5 in #230

chore: add funding.json manifest for FLOSS/fund by @shenxianpeng in #231

test: measure coverage by package name and cover the worker log fallback by @shenxianpeng in #222

📝 Documentation updates

docs: update PR review caveats for reused reviews by @shenxianpeng in #234

feat: migrate to git-bot-feedback by @2bndy5 in #226

... (truncated)

Commits

0df0602 fix: support a --repo-root in a sub-folder of the git repo (#247)
8f369e7 test: cover missing-token exits and 404 responses, keep tests off real GitHub...
55cf791 fix: stop changing into --repo-root and only accept one inside the working ...
2a37247 build(deps): bump certifi from 2025.10.5 to 2026.10.19 (#244)
d08ee70 chore(dev): test against Python 3.15 and the 3.16 pre-release (#241)
188e1fd chore: count only binary downloads in funding.json (#243)
79c3660 fix: raise when git cannot read the original file (#242)
db00cfb build: bump git-bot-feedback from 0.2.6 to 0.2.9 (#239)
0619384 fix: replace pygit2 with a git diff subprocess (#240)
a5bc7db docs: fix outdated CI note, docs build steps and CLI doc generation (#238)
Additional commits viewable in compare view

github-actions · 2026-10-15T18:53:55Z

Cpp-Linter Report ⚠️

Some files did not pass the configured checks!

clang-format (v16.0.6) reports: 2 file(s) not formatted

docs/examples/demo/demo.cpp
docs/examples/demo/demo.hpp

clang-tidy (v16.0.6) reports: 7 concern(s)

docs/examples/demo/demo.cpp:3:10: warning: [modernize-deprecated-headers]

inclusion of deprecated C++ header 'stdio.h'; consider using 'cstdio' instead
```
#include <stdio.h>
         ^~~~~~~~~
         <cstdio>
```
docs/examples/demo/demo.cpp:8:5: warning: [modernize-use-trailing-return-type]

use a trailing return type for this function
```
int main(){
~~~ ^
auto       -> int
```
docs/examples/demo/demo.cpp:10:13: warning: [readability-braces-around-statements]

statement should be inside braces
```
    for (;;) break;
            ^
             {
```
docs/examples/demo/demo.cpp:13:5: warning: [cppcoreguidelines-pro-type-vararg]

do not call c-style vararg functions
```
    printf("Hello world!\n");
    ^
```
docs/examples/demo/demo.hpp:6:11: warning: [modernize-use-default-member-init]

use default member initializer for 'useless'
```
    char* useless;
          ^
                 {"\0"}
```
docs/examples/demo/demo.hpp:7:9: warning: [modernize-use-default-member-init]

use default member initializer for 'numb'
```
    int numb;
        ^
            {0}
```

docs/examples/demo/demo.hpp:11:11: warning: [modernize-use-trailing-return-type]

use a trailing return type for this function

    void *not_useful(char *str){useless = str;}
    ~~~~~~^
    auto                        -> void *

_{✨ Powered by cpp-linter -- ⭐ Star • ❤️ Sponsor • 💬 Feedback}

2bndy5 · 2026-10-15T19:12:40Z

We should probably run this branch through the test repo.

shenxianpeng · 2026-10-15T20:07:51Z

I agree

shenxianpeng · 2026-10-19T18:52:12Z

Ran this branch through the test repo (temporary PR cpp-linter/test-cpp-linter-action#64, now closed), next to a baseline of main (cpp-linter 1.14.1), on push and pull_request events.

Works the same as 1.14.1 on ubuntu-latest, ubuntu-24.04-arm, macos-latest and windows-latest:

thread comment: posted on the PR and updated in place on re-runs; on push it is a commit comment. New footer links present.
tidy-review / format-review: posted; on re-runs, comments already posted are reused and no new review is posted when nothing is new.
file annotations, step summary and the checks-failed outputs match the baseline.
auto-fix pushes the formatting commit.

Runs: https://github.com/cpp-linter/test-cpp-linter-action/actions/runs/38806552518 (pull_request), https://github.com/cpp-linter/test-cpp-linter-action/actions/runs/38806544496 (push)

Not caused by this PR:

windows-11-arm fails on main too: pygit2 1.18.1 has no win-arm64 wheel and the source build can't find git2.h.
The odd suggestions on [DO NOT MERGE] test cpp-linter-action#501 (cpp-linter 1.15.0) test-cpp-linter-action#64 (include reorder split into remove + add; the } insertion landing on line 26) come from v1 patch logic that is unchanged since 1.14.1. One suggestion was stale because my auto-fix job pushed while the review was running.
Cosmetic: the review body now contains the  marker twice (cpp-linter adds it and git-bot-feedback adds it again).

Found since, and the reason to hold this PR:

GitHub Enterprise Server: with 1.15.0, git-bot-feedback joins API paths onto GITHUB_API_URL with Url::join, which drops the /v3 segment when the URL has no trailing slash (https://ghe.example.com/api/v3 -> https://ghe.example.com/api/repos/...), so API calls 404. Reproduced locally against a fake API server. 1.14.1 is fine.
--ignore=build no longer skips a nested src/build/ directory. Is this intended with the git-bot-feedback file filter?

Suggest keeping this open until a 1.15.x release fixes the GHES URL.

2bndy5 · 2026-10-19T21:52:05Z

Cosmetic: the review body now contains the  marker twice (cpp-linter adds it and git-bot-feedback adds it again)

This should not be happening. I'll review the code in git-bot-feedback. It should automatically detect the marker is present before prepending it. Maybe that check was only applied to thread-comments.

GitHub Enterprise Server: with 1.15.0, git-bot-feedback joins API paths onto GITHUB_API_URL with Url::join, which drops the /v3 segment when the URL has no trailing slash (https://ghe.example.com/api/v3 -> https://ghe.example.com/api/repos/...), so API calls 404. Reproduced locally against a fake API server. 1.14.1 is fine.

Needs to be raised in git-bot-feedback repo.

--ignore=build no longer skips a nested src/build/ directory. Is this intended with the git-bot-feedback file filter?

Yes and no. Depends on what exactly was observed. git-bot-feedback will still traverse ignore paths in case there is an unignored rule for a nested file/folder.

Technically speaking, I think it is wrong if v1.14 ignored src/build when the ignore rule is only build, because it is not a glob pattern and build/ is different from src/build/.

Ultimately, there should be no files reported from /src/build (to borrow your example) if the --ignore=src/build and there is no unignored rules like !/src/build/*/CMakeCache.txt. There are tests to ensure this behavior, so if there's a regression, I need a reproduction case.

2bndy5 · 2026-10-20T02:05:55Z

--ignore=build no longer skips a nested src/build/ directory. Is this intended with the git-bot-feedback file filter?

I looked into this more. First, I could not find evidence of this problem in the linked CI runs. Secondly, I think you stumbled upon a bug in v1.14. An ignore pattern of build is taken as a relative path to the repo-root. So, --ignore=build should not exclude sources from src/build/. However, --ignore=*/build/ should exclude from src/build/

I guess switching to git-bot-feedback abstracted (and fixed) that problem in v1.15. 🎉

I raised issues for the other 2 findings.

windows-11-arm fails on main too: pygit2 1.18.1 has no win-arm64 wheel and the source build can't find git2.h

Believe it or not, I'm the reason pygit2 now builds windows wheels with cibuildwheels in their CI. But when trying to add windows-arm64 builds, the build env needed too much special attention to feasibly create win-arm64 wheels. Maybe that's changed since the arm containers migrated to GH-controlled repo... IDK.

We could instead just remove pygit2 and switch to difflib or the third-party (pure-python) unidiff lib. Because the git-bot-feedback lib now does most of our diff parsing about changed files. pygit2 is really only used to get the diff between original source and clang tools' fixes.

Follow-up to #140. Before: GraphQL requests used `api_url.join("/graphql")`. The leading `/` replaces the whole path, so on GitHub Enterprise Server, where the REST API is at `https://<host>/api/v3` and GraphQL is at `https://<host>/api/graphql`, every GraphQL request (fetching existing review threads, resolving or deleting old review comments, hiding outdated reviews) went to `https://<host>/graphql` and failed. After: the client reads the GraphQL endpoint from `GITHUB_GRAPHQL_URL`, which GitHub runners set on both github.com (`https://api.github.com/graphql`) and GHES (`https://<host>/api/graphql`). When it is not set, it falls back to `https://api.github.com/graphql`, the same way `GITHUB_API_URL` falls back to `https://api.github.com`. | Runner | GraphQL URL before | GraphQL URL after | | --- | --- | --- | | github.com | `https://api.github.com/graphql` | `https://api.github.com/graphql` (unchanged) | | GHES | `https://<host>/graphql` | `https://<host>/api/graphql` | How: `GithubApiClient` stores the parsed `GITHUB_GRAPHQL_URL` in a `graphql_url` field, used by all three GraphQL calls in `graphql.rs`. The unit test `ensure_api_url_has_trailing_slash` checks the field, and `tests/github_pr_reviews.rs` points `GITHUB_GRAPHQL_URL` at the mock server. Found while testing cpp-linter-action with cpp-linter 1.15.0 (cpp-linter/cpp-linter-action#501).  ## Summary by CodeRabbit * **Bug Fixes** * Improved GitHub integration when retrieving, closing, or hiding outdated review comments. * Added support for correctly connecting to GraphQL endpoints across GitHub.com, GitHub Enterprise, and local server configurations.

This pulls in fixes for bugs found and reported upstream in cpp-linter/cpp-linter-action#501 See also [GBF bindings/python/CHANGELOG](https://github.com/2bndy5/git-bot-feedback/blob/main/bindings/python/CHANGELOG.md)

This pulls in fixes for bugs found and reported upstream in cpp-linter/cpp-linter-action#501 See also [GBF bindings/python/CHANGELOG](https://github.com/2bndy5/git-bot-feedback/blob/main/bindings/python/CHANGELOG.md) Co-authored-by: Xianpeng Shen <xianpeng.shen@gmail.com>

This pulls in some fixes for bugs reported via python integration in cpp-linter/cpp-linter-action#501 See [GBF CHANGELOG.md](https://github.com/2bndy5/git-bot-feedback/blob/main/CHANGELOG.md) for more detail.   ## Summary by CodeRabbit - **Bug Fixes** - Improved reliability of automated code review feedback integrations. - **Tests** - Updated integration test configuration to better validate GraphQL-based feedback workflows.

shenxianpeng · 2026-10-23T17:15:46Z

@dependabot recreate

Bumps the org group with 1 update in the / directory: [cpp-linter](https://github.com/cpp-linter/cpp-linter). Updates `cpp-linter` from 1.14.1 to 1.15.1 - [Release notes](https://github.com/cpp-linter/cpp-linter/releases) - [Commits](cpp-linter/cpp-linter@v1.14.1...v1.15.1) --- updated-dependencies: - dependency-name: cpp-linter dependency-version: 1.15.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: org ... Signed-off-by: dependabot[bot] <support@github.com>

shenxianpeng · 2026-10-25T16:09:35Z

End-to-end test of this PR plus clang-tools 2.0.0: no regressions found.

What was tested: cpp-linter-action at fc065f1 (this PR's head, cpp-linter 1.15.1, plus clang-tools==2.0.0, which isn't in this PR yet) against main (f16b974, cpp-linter 1.14.1 + clang-tools 1.3.0), in cpp-linter/test-cpp-linter-action#65.

Same results as main (push run)

36 pairs: ubuntu-latest, macos-latest and windows-latest × clang 12–23. checks-failed, clang-format-checks-failed and clang-tidy-checks-failed match in every pair.
ubuntu-24.04-arm, macos-latest and windows-latest with clang 20: same counts as main.
windows-11-arm now works. On main it fails because uv has to build pygit2 1.18.1 from source (there's no win-arm64 wheel). With 1.15.1 there's no pygit2, and clang-tools 2.0.0 installs the windows-arm64 static binaries of clang-tidy and clang-format 20.1.8.

clang-tools 2.0.0

On Windows, and for clang 12/13 on Linux and macOS, the static binaries are now the newest patch release of each major version (for example 14.0.6, 18.1.8, 23.1.3 instead of 14.0.0, 18.1.5, 23.1.0). The clang-resource-headers bundle is downloaded with them. On this test code the counts didn't change.
Where the runner already has the requested version (apt, Homebrew), it's used as before.

On a pull request (PR run)

Thread comment (updated in place), file annotations and step summary: OK.
tidy-review + format-review: one review with the full clang-tidy and clang-format patches in its summary, and inline suggestions on the changed lines. The suggestions, which 1.15.1 now builds with git diff instead of pygit2, are correct.
auto-fix: pushed one formatting commit with the right clang-format change.

Two notes for the release notes, both from cpp-linter 1.15.x:

ignore: build only matches build/ at the repo root now. Use **/build for nested folders (*/build/ does not match anything, */build only one level down).
A relative database path is resolved against the workspace, not repo-root, and repo-root must be inside the workspace.

Generated by Claude Code

shenxianpeng · 2026-10-25T16:48:27Z

@dependabot recreate

dependabot · 2026-10-25T16:49:35Z

Looks like cpp-linter is updatable in another way, so this is no longer needed.

dependabot Bot requested a review from a team as a code owner October 15, 2026 18:53

dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 15, 2026

dependabot Bot requested review from shenxianpeng and removed request for a team October 15, 2026 18:53

dependabot Bot added semver:minor Overrides the PR title: bump the minor version python:uv Pull requests that update python:uv code labels Oct 15, 2026

shenxianpeng mentioned this pull request Oct 15, 2026

[DO NOT MERGE] test cpp-linter-action#501 (cpp-linter 1.15.0) cpp-linter/test-cpp-linter-action#64

Closed

shenxianpeng force-pushed the dependabot/uv/org-d4db3e9bba branch from 7319830 to 53a13e5 Compare October 18, 2026 21:31

shenxianpeng mentioned this pull request Oct 20, 2026

fix: use GITHUB_GRAPHQL_URL for GraphQL requests 2bndy5/git-bot-feedback#143

Merged

2bndy5 mentioned this pull request Oct 20, 2026

build: bump git-bot-feedback from 0.2.6 to 0.2.9 cpp-linter/cpp-linter#239

Merged

shenxianpeng mentioned this pull request Oct 20, 2026

fix: replace pygit2 with a git diff subprocess cpp-linter/cpp-linter#240

Merged

This comment was marked as outdated.

Sign in to view

This comment was marked as resolved.

Sign in to view

2bndy5 mentioned this pull request Oct 21, 2026

build: bump git-bot-feedback from v0.8.6 to v0.8.8 cpp-linter/cpp-linter-rs#515

Merged

dependabot Bot changed the title ~~chore(deps-dev): bump cpp-linter from 1.14.1 to 1.15.0 in the org group~~ chore(deps-dev): bump cpp-linter from 1.14.1 to 1.15.1 in the org group across 1 directory Oct 23, 2026

dependabot Bot force-pushed the dependabot/uv/org-d4db3e9bba branch from ac143e0 to da7f4c5 Compare October 23, 2026 17:17

2bndy5 approved these changes Oct 24, 2026

View reviewed changes

shenxianpeng mentioned this pull request Oct 25, 2026

Moving toward v3 #283

Open

2 of 3 tasks

dependabot Bot closed this Oct 25, 2026

dependabot Bot deleted the dependabot/uv/org-d4db3e9bba branch October 25, 2026 16:49

shenxianpeng mentioned this pull request Oct 25, 2026

chore(deps-dev): bump the org group across 1 directory with 2 updates #512

Merged

Navigation Menu

Repository navigation

chore(deps-dev): bump cpp-linter from 1.14.1 to 1.15.1 in the org group across 1 directory - #501

chore(deps-dev): bump cpp-linter from 1.14.1 to 1.15.1 in the org group across 1 directory#501
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/org-d4db3e9bba

dependabot Bot commented on behalf of github Oct 15, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 15, 2026 •

edited

Loading

Uh oh!

2bndy5 commented Oct 15, 2026

Uh oh!

shenxianpeng commented Oct 15, 2026

Uh oh!

shenxianpeng commented Oct 19, 2026 •

edited by 2bndy5

Loading

Uh oh!

2bndy5 commented Oct 19, 2026 •

edited

Loading

Uh oh!

2bndy5 commented Oct 20, 2026 •

edited

Loading

Uh oh!

This comment was marked as outdated.

This comment was marked as resolved.

shenxianpeng commented Oct 23, 2026

Uh oh!

shenxianpeng commented Oct 25, 2026 •

edited

Loading

Uh oh!

shenxianpeng commented Oct 25, 2026

Uh oh!

dependabot Bot commented on behalf of github Oct 25, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

dependabot Bot commented on behalf of github Oct 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v1.15.1

🐛 Bug fixes

📝 Documentation updates

✍ Other changes

📦 Dependency updates

v1.15.0

🚀 New features and improvements

🐛 Bug fixes

👷 Changes for developers

📝 Documentation updates

Uh oh!

github-actions Bot commented Oct 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Cpp-Linter Report ⚠️

Uh oh!

2bndy5 commented Oct 15, 2026

Uh oh!

shenxianpeng commented Oct 15, 2026

Uh oh!

shenxianpeng commented Oct 19, 2026 • edited by 2bndy5 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

2bndy5 commented Oct 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

2bndy5 commented Oct 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as outdated.

This comment was marked as resolved.

shenxianpeng commented Oct 23, 2026

Uh oh!

shenxianpeng commented Oct 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shenxianpeng commented Oct 25, 2026

Uh oh!

dependabot Bot commented on behalf of github Oct 25, 2026

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

dependabot Bot commented on behalf of github Oct 15, 2026 •

edited

Loading

github-actions Bot commented Oct 15, 2026 •

edited

Loading

shenxianpeng commented Oct 19, 2026 •

edited by 2bndy5

Loading

2bndy5 commented Oct 19, 2026 •

edited

Loading

2bndy5 commented Oct 20, 2026 •

edited

Loading

shenxianpeng commented Oct 25, 2026 •

edited

Loading